commit: Support generating commits with no parent, or a custom one
authorColin Walters <walters@verbum.org>
Fri, 25 Mar 2016 15:03:32 +0000 (11:03 -0400)
committerColin Walters (automation) <walters+githubbot@verbum.org>
Tue, 29 Mar 2016 14:31:29 +0000 (14:31 +0000)
commitc6b4ecd474257fa192743096a8dc94f6ae1e7be7
treec57a608643e9237c80d1478d34a12ce534d6f9f0
parenta50df5daf75cd03dae506eb8e5d2e57f71bb3de3
commit: Support generating commits with no parent, or a custom one

When I'm doing local development builds, it's quite common for me not
to want to accumulate history.  There are also use cases for this on
build servers as well.

In particular, using this, one could write a build system that didn't
necessarily need to have access to (a copy of) the OSTree repository.
Instead, the build system would determine the last commit ID on the
branch, and pass that to a worker node, then sync the generated
content back.

The API supported generating custom commits that don't necessarily
reference the previous commit on the same branch, let's just expose
this in the command line for convenience.

I plan to also support this rpm-ostree.

Closes: #223
Approved by: jlebon
src/ostree/ot-builtin-commit.c
tests/basic-test.sh